Using SourceSafe with SM

• SourceSafe version - Source Manager requires SourceSafe 3.0 or greater, since prior versions of SourceSafe did not support use of 'ckid' resources.
• Check everything in first - To get started using Source Manager with existing SourceSafe projects, first check in all your modified files in the same way you would before using Source Manager.  Then continue with the directions below.
• Configuring UserStartupTS - This is a configuration file which ToolServer looks for and executes when it starts up.  The purpose of the file is to define certain symbols in ToolServer, which the SourceSafe SS tool reads when it executes certain commands, and to define your local CheckOut dirs to be associated with SourceSafe projects (Source Manager is the one who reads these, not SourceSafe).  A sample UserStartupTS file called "Sample UserStartupTS" comes with Source Manager.  You should modify this file to tailor it to your system, following the well-defined directions above each item in that sample file. Then place it in the same folder as ToolServer, or in the "MPW Preferences" folder of your System folder.
• Configuring srcsafe.ini - This is another configuration file.  It comes with SourceSafe and is located in the SourceSafe folder, probably called "SrcSafe".  You'll need to change this file only if it's not currently configured to use ckid's instead of Finder locks to denote read-only files.  One quick way to tell is by dragging one of your existing project files (if you have any) onto SM.  When it shows up in the table, see if it says "orphan" in the Project column.  If so, you want to delete all your local project files, insert the following two lines into "srcsafe.ini":
Use_ReadOnly = No
Use_CKID = Yes
and then Get all the files back from the database. When you do this, your local files will have 'ckid' resources and won't be locked.
• Ready to go - Startup Source Manager and choose "Launch ToolServer".  If there is no Source Manager Prefs file in your system folder, SM will automatically ask SourceSafe for a list of the currently defined projects (this can potentially take a few minutes, if there are lots of projects).  If there is a prefs file, just manually request a fresh project list by selecting Refresh from the Projects submenu.  If you've configured your UserStartupTS file properly, you'll see a list of all existing SourceSafe projects in the "Projects" submenu, with the current project checked.  At this point, you should define local checkout dirs for each project your interested in, so choose Edit CheckOut Dirs and enter the dirs.  When you close this window, you'll be all set to get files from the database.  Select the project of interest, notice that your CheckOut Dirs submenu switches to the local dir you just defined for that project, and then choose Get All From, selecting the first item in the menu (the current project).   That's it.  Whew.